Grokking SQL for Tech Interviews
Rate this course
Ask Author
Contribute
Back to course home

1% completed

Vote For New Content
Introduction
Course Overview
What is RDBMS?
What is SQL?
A Quick Review of SQL
Read data from table
WHERE Clause
Operators
Handle NULLs in SQL
DISTINCT Clause
ORDER BY Clause
LIMIT and OFFSET
GROUP BY
HAVING
Aggregate Functions
Order of Execution
Order of SQL Query Execution
SQL Functions
Number Functions
String Functions
Date Functions
Nested Queries
Nested Query
Types of Subqueries
JOINS
Introduction
INNER JOIN
LEFT OUTER JOIN
RIGHT OUTER JOIN
FULL OUTER JOIN
SELF JOIN
SET Operations
What are SET operations?
UNION
INTERSECT
EXCEPT
A Quick Review of DDL
Keys in SQL
CREATE
ALTER
DROP
TRUNCATE
Indexes
A Quick Review of DML
INSERT
UPDATE
DELETE
Database Backup & Restore
Backup Database
Restore Database
Interview Problems - Easy
1. Major Cities
2. Not boring movies
3. Triangle Judgement
4. Biggest Single Number
5. Product Sales Analysis I
6. Product Sales Analysis II
7. Game Play Analysis I
8. Game Play Analysis II
9. Queries Quality and Percentage
10. Average Selling Price
11. Weather Type in Each Country
12. Students and Examinations
13. Ads Performance
14. Group Sold Products By The Date
15. Employee Email Verification
16. Sellers With No Sales
17. Average Time of Process
18. Find Followers Count
19. Ad-Free Sessions
20. Bikes Last Time Used
21. Daily User Engagement Levels
22. Employee Attendance Record
23. Library Book Loans
24. Customer Purchase Summary
25. Long Comments (Easy)
26. Unused Accounts
27. Patient Appointment No-Shows
28. Books and Authors
29. High School Attendance
30. Employee Absences
31. Green Product Identification (Easy)
32. Employee Department Exclusion (Easy)
33. Sales Person (Easy)
34. Employee Task Tracking (Easy)
Interview Problems - Medium
1. Winning Candidate
2. Second Degree Follower
3. 2nd Highest Salary
4. Game Play Analysis III
5. Game Play Analysis IV
6. Active Businesses
7. Product Price on a Specific Date
8. Monthly Transactions II
9. Team Scores in Football Tournament
10. Page Recommendations
11. Running Total for Different Genders
12. Evaluate Boolean Expression
13. Active Users
14. Find Interview Candidates
15. Suspicious Bank Accounts
16. Order Fulfillment Rate (Medium)
17. Last Person to Fit in the Elevator (Medium)
18. Retail Expansion Analysis (Medium)
19. Employee Collaboration Networks (Medium)
20. Second Fastest Time in Races (Medium)
1. Trips and Users
2. Human Traffic of Stadium
3. Students Report By Geography
4. Game Play Analysis V
5. Number of Transactions per Visit
6. Find the Quiet Students in All Exams
7. First and Last Call On the Same Day
8. Build the Equation
9. Longest Winning Streak
10. Dynamic Pivoting of a Table
11. Dynamic Unpivoting of a Table
12. Generate the Invoice
13. Popularity Percentage
14. Viewers Turned Streamers
15. Status of Flight Tickets
1. High Performing Employees (Easy)
2. Student Course Averages (Easy)
3. Library Book Checkout Percentage (Easy)
4. Employee Performance and Improvement Rate (Easy)
5. Find Popular Posts (Easy)
6. Main Office Assignment for Each Employee (Easy)
7. Rectangle Validation (Easy)
8. Library Book Checkouts by Date (Easy)
9. Same-Day Appointment Fulfillment (Medium)
10. Departments with High Earning Employees (Medium)
11. Students Who Attended All Courses (Medium)
12. Library Book Checkouts First Year (Medium)
13. Repeated Values in Sequence (Medium)
14. School Top Achievers by Subject (Hard)
10. Page Recommendations

Problem

Table: Friendship

+---------------+---------+
| Column Name   | Type    |
+---------------+---------+
| user1_id      | int     |
| user2_id      | int     |
+---------------+---------+
(user1_id, user2_id) is the primary key (combination of columns with unique values) for this table.
Each row of this table indicates that there is a friendship relation between user1_id and user2_id.

Table: Likes

+-------------+---------+
| Column Name | Type    |
+-------------+---------+
| user_id     | int     |
| page_id     | int     |
+-------------+---------+
(user_id, page_id) is the primary key (combination of columns with unique values) for this table.
Each row of this table indicates that user_id likes page_id.

Problem Definition

Write a solution to recommend pages to the user with user_id = 1 using the pages that his/her friends liked. It should not recommend pages user_1 already liked.

Return result table in any order without duplicates.

Example

Image

Output

Image

Try It Yourself

MYSQL

. . . .

Friendship =

Likes =

Solution

To recommend pages to the user with user_id = 1 based on the pages liked by their friends, while excluding the pages that user 1 has already liked, we can follow a systematic approach. This solution leverages SQL's WITH clause (Common Table Expressions), UNION ALL, and subqueries to efficiently identify the relevant pages for recommendation.

  • Identify All Friends of User 1: Retrieve all users who are friends with user 1 by examining both directions of the friendship relation.
  • Find Pages Liked by These Friends: Extract all pages liked by the identified friends.
  • Exclude Pages Already Liked by User 1: Ensure that the recommended pages do not include any pages that user 1 has already liked.
  • Select Distinct Recommended Pages: Remove any duplicate page entries to provide a clean list of recommendations.

SQL Query

WITH friends AS ( (SELECT user2_id AS friend FROM Friendship WHERE user1_id = 1) UNION ALL (SELECT user1_id AS friend FROM Friendship WHERE user2_id = 1) ) SELECT DISTINCT page_id AS recommended_page FROM Likes WHERE user_id IN (SELECT friend FROM friends) AND page_id NOT IN ( SELECT page_id FROM Likes WHERE user_id = 1 );

Step-by-Step Approach

Step 1: Identify All Friends of User 1

Retrieve all user IDs that are friends with user 1 by checking both user1_id and user2_id in the Friendship table.

SQL Query:

WITH friends AS ( (SELECT user2_id AS friend FROM Friendship WHERE user1_id = 1) UNION ALL (SELECT user1_id AS friend FROM Friendship WHERE user2_id = 1) )

Explanation:

  • WITH friends AS (...):
    • Defines a Common Table Expression (CTE) named friends to store the list of user IDs who are friends with user 1.
  • SELECT user2_id AS friend FROM Friendship WHERE user1_id = 1:
    • Selects all user2_ids where user1_id is 1, indicating that these users are friends initiated by user 1.
  • UNION ALL:
    • Combines the results from both SELECT statements, ensuring that all friends are included without eliminating duplicates (though duplicates are unlikely in this context).
  • SELECT user1_id AS friend FROM Friendship WHERE user2_id = 1:
    • Selects all user1_ids where user2_id is 1, capturing friendships initiated by other users towards user 1.

Output After Step 1:

+---------+ | friend | +---------+ | 2 | | 3 | | 4 | | 6 | +---------+

Step 2: Find Pages Liked by These Friends

Retrieve all page_ids that have been liked by the identified friends.

SQL Query:

SELECT DISTINCT page_id AS recommended_page FROM Likes WHERE user_id IN (SELECT friend FROM friends)

Explanation:

  • SELECT DISTINCT page_id AS recommended_page:
    • Selects unique page_ids from the Likes table and aliases them as recommended_page to ensure no duplicates in the recommendations.
  • WHERE user_id IN (SELECT friend FROM friends):
    • Filters the Likes records to include only those where the user_id is in the list of friends identified in Step 1.

Output After Step 2:

+-----------------+ | recommended_page| +-----------------+ | 23 | | 24 | | 56 | | 33 | | 77 | | 88 | +-----------------+

Step 3: Exclude Pages Already Liked by User 1

Ensure that the recommended pages do not include any pages that user 1 has already liked.

SQL Query:

AND page_id NOT IN ( SELECT page_id FROM Likes WHERE user_id = 1 )

Explanation:

  • AND page_id NOT IN (...):
    • Further filters the recommended pages by excluding any page_id that appears in the subquery.
  • Subquery:
    • SELECT page_id FROM Likes WHERE user_id = 1:
      • Retrieves all page_ids that user 1 has already liked.
    • NOT IN:
      • Ensures that none of the pages already liked by user 1 are included in the final recommendations.

Output After Step 3:

+-----------------+ | recommended_page| +-----------------+ | 23 | | 24 | | 56 | | 33 | | 77 | +-----------------+

Ensure that each recommended page appears only once in the final output, removing any duplicates that may arise from multiple friends liking the same page.

SQL Query:

SELECT DISTINCT page_id AS recommended_page FROM Likes WHERE user_id IN (...);

Explanation:

  • SELECT DISTINCT page_id AS recommended_page:
    • Selects unique page_ids to avoid duplicate recommendations.

Final Output:

+-----------------+ | recommended_page| +-----------------+ | 23 | | 24 | | 56 | | 33 | | 77 | +-----------------+
9. Team Scores in Football Tournament
11. Running Total for Different Genders
Mark as Completed

On this page

Problem

Problem Definition

Example

Output

Try It Yourself

Solution

SQL Query

Step-by-Step Approach